FLPATH-4285 | [DCM] Server-side pagination not implemented - #4155
Conversation
|
Important This PR includes changes that affect public-facing API. Please ensure you are adding/updating documentation for new features or behavior. Changed Packages
|
PR Summary by QodoAdd server-side cursor pagination across all DCM tabs
AI Description
Diagram
High-Level Assessment
Files changed (34)
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #4155 +/- ##
==========================================
+ Coverage 58.06% 58.19% +0.13%
==========================================
Files 2411 2415 +4
Lines 96367 96541 +174
Branches 26856 26895 +39
==========================================
+ Hits 55953 56181 +228
+ Misses 40215 40130 -85
- Partials 199 230 +31
*This pull request uses carry forward flags. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Code Review by Qodo
1.
|
f14477d to
9c0b53d
Compare
3c26133 to
d61c0d0
Compare
mareklibra
left a comment
There was a problem hiding this comment.
-
No
usePaginatedCrudTabunit tests, nobuildPaginationQuerytests, no search+resetCursorregression, andProvidersClient.teststill only asserts unpaginatedGET /providers. Worth adding at least query-param client coverage and the search/Next regression above. -
Cursor controls default to
[5, 15, 25]while the Table pager uses[5, 10, 25]. Align them unless 15 is intentional. -
Providers/Catalog loadFns re-fetch service-types/catalog-items (capped at 25) on every Next/Prev. Load dropdown options once (separate effect) to avoid redundant traffic.
mareklibra
left a comment
There was a problem hiding this comment.
Adding new comments. Something is left from the last time.
|



Summary
Add server-side cursor pagination to all DCM tabs.
Previously only Service Types, Catalog Items, and Instances fetched data page-by-page. Providers, Policies, and Resources loaded everything in a single call, silently dropping records beyond the first page.
What changed
usePaginatedFetch(read-only layout preserved).dcm-common— extractedbuildPaginationQueryutility;listProvidersandlistPoliciesnow accept optionalPaginationParams;next_page_tokenmade optional on list response types to match real backend behaviour.max_page_size: 25.ProvidersTabContent.test.tsxandResourcesTabContent.test.tsx; extendedPoliciesTabContent.test.tsxwith cursor navigation tests.common.previousPage/common.nextPageto all locale files.